gDEBugger User Guide
| gDEBugger User Guide |
The Call Stack view displays the thread call stack that led to the function call suspending the debugged process run.
The thread call stack is displayed as a list. Each list item represents a stack frame and displays the details of the function call that formed the stack frame.
The items (function calls) are ordered bottom up: a function is placed directly above the function that called it.
Selecting a list item will present the properties it represents in the Properties view.
The name of the selected function.
The source code file path in which this function code resides.
The line number in the above source code file where a call to the next stack frame function appears.
The name of the module containing the selected function binary code.
The address, in debugged process virtual address space, from which a call to the next stack frame function appears.
The address, in debugged process virtual address space, in which the selected function binary code starts.
The availability of the above fields depends on the type of debug information the debugged process uses. The best results are obtained when debugging a process compiled in debug configuration and generating a .pdb (program database) file.
Double clicking on a list line opens the Source Code Viewer, presenting the appropriate function call source code. The source code line where a call to the next stack frame function appears is highlighted.